fix: #36 adjust docker-compose paths and network connectivity#37
Merged
Benevanio merged 1 commit intoMar 30, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Resumo
Este PR corrige falhas críticas no docker-compose.yml que impediam a inicialização correta do backend e o acesso ao frontend via navegador na máquina hospedeira.
Alterações Realizadas
Backend: Corrigido o command para apontar para o ponto de entrada correto do servidor: de backend/index.js para backend/src/server.js. Isso alinha o container com a estrutura atual do projeto.
Frontend: Adicionado o parâmetro --host 0.0.0.0 ao comando de execução do Vite. Isso permite que o servidor aceite conexões externas ao container, possibilitando o acesso via localhost:5173.
Refatorado o comando para utilizar explicitamente o gerenciamento de workspaces (--workspace=frontend), garantindo que as dependências e o contexto de execução sejam respeitados corretamente.
🐛 Problemas Resolvidos (Issues)
Fecha #36 - Falha na inicialização e falta de acessibilidade externa via Docker Compose
🧪 Como testar?
Certifique-se de que não há containers antigos rodando: docker-compose down.
Suba o ambiente: docker-compose up --build.
Validar Backend: Verifique nos logs se o container vagas-backend iniciou sem erros de "file not found".
Validar Frontend: Acesse http://localhost:5173 no seu navegador e verifique se a aplicação carrega corretamente.